Real time video editing

ABSTRACT

Examples of the present disclosure improve the functionality of electronic software and systems by enhancing users&#39; experience of utilizing a camera of a client device. The technical problem of generating a video that has the starting point later in time than the starting time of the associated recording session is addressed by providing a real time video editing functionality. In some examples, a real time video editing functionality is in the form of a real time video editor provided by a messaging system for exchanging data over a network.

CLAIM OF PRIORITY

This application claims the benefit of priority to U.S. ProvisionalApplication Ser. No. 63/198,145, filed Sep. 30, 2020, which isincorporated herein by reference in its entirety.

BACKGROUND

The input/output I/O components of a client device often include one ormore cameras (with still image/photograph and video capabilities).Camera applications provided with some mobile devices, such assmartphones, may include a feature that permits setting a timer withrespect to a video recording session. For example, a user may set thetimer to start the recording after 5 seconds, which would give them timeto move away from the smartphone, to the area that is to be captured ina video. If such timer feature is not engaged, a user may simply pressthe record button and walk to the area that is being captured by thedigital image sensor of the camera. The resulting recorded video maythen include the first few seconds worth of frames where the user is notin the frames. In another example, where a user is recording a sportsevent, some exciting action may occur only some time after the recordinghas started. In both of these examples, the first part of the recording(where the user is not in the frames or when there is nothing excitinghas yet happened in the sports event) may be of little or no interest tothe user.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. To easily identifythe discussion of any particular element or act, the most significantdigit or digits in a reference number refer to the figure number inwhich that element is first introduced. Some nonlimiting examples areillustrated in the figures of the accompanying drawings in which:

FIG. 1 is a diagrammatic representation of a networked environment inwhich the present disclosure may be deployed, in accordance with someexamples.

FIG. 2 is a diagrammatic representation of a messaging system, inaccordance with some examples, that has both client-side and server-sidefunctionality.

FIG. 3 is a diagrammatic representation of a data structure asmaintained in a database, in accordance with some examples.

FIG. 4 is a diagrammatic representation of a message, in accordance withsome examples.

FIG. 5 is a flowchart for an access-limiting process, in accordance withsome examples.

FIG. 6 is a flowchart illustrating a method for real time video editingin accordance with some examples.

FIG. 7 is a diagrammatic representation of a camera view user interfacedisplaying the output of the digital image sensor of a camera, inaccordance with some examples.

FIG. 8 is a diagrammatic representation of a swipe gesture directed atthe camera view user interface, in accordance with some examples.

FIG. 9 is a diagrammatic representation of a of a rewind actionimitation in a camera view user interface, in accordance with someexamples.

FIG. 10 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions may be executed forcausing the machine to perform any one or more of the methodologiesdiscussed herein, in accordance with some examples.

DETAILED DESCRIPTION

Examples of the present disclosure improve the functionality ofelectronic software and systems by enhancing users' experience ofutilizing a camera of a client device. Examples of the presentdisclosure further improve the functionality of electronic software andsystems by reducing the amount of storage space and processing resourcesassociated with generating a video file based on a sequence of framescaptured in the process of video recording. In some examples, thereducing of the amount of storage space and processing resourcesrequired for creating a video file results from discarding some of therecorded video frames before creating and storing the video file.

In order to start and stop video recording, a user may activate thecapture button provided in the user interface (UI) of the associatedcamera application. The camera of the client device, such as asmartphone, for example, captures the output of the digital image sensorof the camera, and, upon the ending of the recording session, the systemgenerates a video file (also referred to as simply a video) using framescaptured during the video recording process. The resulting video can bethen saved and stored for future viewing. However, there are times whena user may wish to view the already-recorded frames, while the recordingis still in progress. Furthermore, as mentioned above, depending on thecircumstances surrounding a recording session, a recorded video mayinclude a portion of frames at the beginning of the video that are oflittle or no value to the user.

The technical problem of generating a video that has the starting pointlater in time than the starting time of the associated recording sessionis addressed by providing a real time video editing functionality. Insome examples, a real time video editing functionality is in the form ofa real time video editor provided by a messaging system for exchangingdata over a network, which is described further below, with reference toFIG. 1-5 .

The use of a real time video editor can be described as follows. A userstarts the video recording process by activating the capture buttonprovided in the camera view user interface (UI) of the associated cameraapplication and determines, at a later time, but while the videorecording is still in progress, that the first portion of the video isnot of interest to them. The user can then perform a predeterminedgesture directed to the camera view UI, such as a left to right swipinggesture, which causes the camera view UI to display the captured framesto be displayed in reverse order, thus imitating or visualizing aprocess of rewinding the video. As the gesture stops, so stops thevisualizing of the rewinding process and the user is presented with oneor more frames corresponding to the place in the sequence of frames, upto which the video was rewound. The user may then be presented with apop-up message requesting to either cancel or to confirm that the videofile that would be created, once the video recording process is stopped,should start not with the first frame in the original sequence of frames(the first frame recorded at the time the recording process wascommenced), but with the one or more frames currently displayed in thecamera view UI, up to which the video was rewound. An example ofoperation of a real time video editor is described further below, withreference to FIG. 6 . As mentioned above, in some examples a real timevideo editor is provided by a messaging system for exchanging data overa network, which is described below.

Networked Computing Environment

FIG. 1 is a block diagram showing an example messaging system 100 forexchanging data (e.g., messages and associated content) over a network.The messaging system 100 includes multiple instances of a client device102, each of which hosts a number of applications, including a messagingclient 104. Each messaging client 104 is communicatively coupled toother instances of the messaging client 104 and a messaging serversystem 108 via a network 106 (e.g., the Internet).

A messaging client 104 is able to communicate and exchange data withanother messaging client 104 and with the messaging server system 108via the network 106. The data exchanged between messaging client 104,and between a messaging client 104 and the messaging server system 108,includes functions (e.g., commands to invoke functions) as well aspayload data (e.g., text, audio, video or other multimedia data).

The messaging server system 108 provides server-side functionality viathe network 106 to a particular messaging client 104. While certainfunctions of the messaging system 100 are described herein as beingperformed by either a messaging client 104 or by the messaging serversystem 108, the location of certain functionality either within themessaging client 104 or the messaging server system 108 may be a designchoice. For example, it may be technically preferable to initiallydeploy certain technology and functionality within the messaging serversystem 108 but to later migrate this technology and functionality to themessaging client 104 where a client device 102 has sufficient processingcapacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client 104. Such operations includetransmitting data to, receiving data from, and processing data generatedby the messaging client 104. This data may include, as examples, messagecontent, client device information, geolocation information, mediaaugmentation and overlays, message content persistence conditions,social network information, live event information, as well as imagesand video captured with a front facing camera of an associated clientdevice using a viewfinder ring flash. Data exchanges within themessaging system 100 are invoked and controlled through functionsavailable via user interfaces (UIs) of the messaging client 104. Forexample, the messaging client 104 can present a camera view UI thatdisplays the output of a digital image sensor of a camera provided withthe client device 102, a camera view UI that displays output of adigital sensor of the camera and a shutter user selectable elementactivatable to start a video recording process. Some examples of acamera view UI are described further below, with reference to FIG. 7-9 .

Turning now specifically to the messaging server system 108, anApplication Program Interface (API) server 110 is coupled to, andprovides a programmatic interface to, application servers 112. Theapplication servers 112 are communicatively coupled to a database server118, which facilitates access to a database 120 that stores dataassociated with messages processed by the application servers 112.Similarly, a web server 124 is coupled to the application servers 112,and provides web-based interfaces to the application servers 112. Tothis end, the web server 124 processes incoming network requests overthe Hypertext Transfer Protocol (HTTP) and several other relatedprotocols.

The Application Program Interface (API) server 110 receives andtransmits message data (e.g., commands and message payloads) between theclient device 102 and the application servers 112. Specifically, theApplication Program Interface (API) server 110 provides a set ofinterfaces (e.g., routines and protocols) that can be called or queriedby the messaging client 104 in order to invoke functionality of theapplication servers 112. The Application Program Interface (API) server110 exposes various functions supported by the application servers 112,including account registration, login functionality, the sending ofmessages, via the application servers 112, from a particular messagingclient 104 to another messaging client 104, the sending of media files(e.g., images or video) from a messaging client 104 to a messagingserver 114, and for possible access by another messaging client 104, thesettings of a collection of media data (e.g., story), the retrieval of alist of friends of a user of a client device 102, the retrieval of suchcollections, the retrieval of messages and content, the addition anddeletion of entities (e.g., friends) to an entity graph (e.g., a socialgraph), the location of friends within a social graph, and opening anapplication event (e.g., relating to the messaging client 104).

The application servers 112 host a number of server applications andsubsystems, including for example a messaging server 114, an imageprocessing server 116, and a social network server 122. The messagingserver 114 implements a number of message processing technologies andfunctions, particularly related to the aggregation and other processingof content (e.g., textual and multimedia content) included in messagesreceived from multiple instances of the messaging client 104. As will bedescribed in further detail, the text and media content from multiplesources may be aggregated into collections of content (e.g., calledstories or galleries). These collections are then made available to themessaging client 104. In some examples, a collection may include an avideo generated using the real time video editor. Other processor andmemory intensive processing of data may also be performed server-side bythe messaging server 114, in view of the hardware requirements for suchprocessing.

The application servers 112 also include an image processing server 116that is dedicated to performing various image processing operations,typically with respect to images or video within the payload of amessage sent from or received at the messaging server 114. Some of thevarious image processing operations may be performed by various ARcomponents, which can be hosted or supported by the image processingserver 116. In some examples, an image processing server 116 isconfigured to provide the functionality of the real time video editordescribed herein.

The social network server 122 supports various social networkingfunctions and services and makes these functions and services availableto the messaging server 114. To this end, the social network server 122maintains and accesses an entity graph 306 (as shown in FIG. 3 ) withinthe database 120. Examples of functions and services supported by thesocial network server 122 include the identification of other users ofthe messaging system 100 with which a particular user has a “friend”relationship or is “following,” and also the identification of otherentities and interests of a particular user.

System Architecture

FIG. 2 is a block diagram illustrating further details regarding themessaging system 100, according to some examples. Specifically, themessaging system 100 is shown to comprise the messaging client 104 andthe application servers 112. The messaging system 100 embodies a numberof subsystems, which are supported on the client-side by the messagingclient 104, and on the sever-side by the application servers 112. Thesesubsystems include, for example, an ephemeral timer system 202, acollection management system 204, an augmentation system 206, and a realtime video editor 208.

The real time video editor 208 is configured to facilitate changing thestarting point of a video recording while the recording process is inprogress, as described in further detail below, with reference to FIG.6-9 .

The ephemeral timer system 202 is responsible for enforcing thetemporary or time-limited access to content by the messaging client 104and the messaging server 114. The ephemeral timer system 202incorporates a number of timers that, based on duration and displayparameters associated with a message, or collection of messages (e.g., astory), selectively enable access (e.g., for presentation and display)to messages and associated content via the messaging client 104. Furtherdetails regarding the operation of the ephemeral timer system 202 areprovided below.

The collection management system 204 is responsible for managing sets orcollections of media (e.g., collections of text, image, video, and audiodata). A collection of content (e.g., messages, including images, video,text, and audio) may be organized into an “event gallery” or an “eventstory.” Such a collection may be made available for a specified timeperiod, such as the duration of an event to which the content relates.For example, content relating to a music concert may be made availableas a “story” for the duration of that music concert. In a furtherexample, a collection may include content, which was generated using oneor more AR components. In some examples, a media content item in acollection is generated using the real time video editor. The collectionmanagement system 204 may also be responsible for publishing an iconthat provides notification of the existence of a particular collectionto the user interface of the messaging client 104.

The collection management system 204 furthermore includes a curationinterface 212 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface212 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certain examples,compensation may be paid to a user for the inclusion of user-generatedcontent into a collection. In such cases, the collection managementsystem 204 operates to automatically make payments to such users for theuse of their content.

The augmentation system 206 provides various functions that enable auser to augment (e.g., annotate or otherwise modify or edit) mediacontent, which may be associated with a message. For example, theaugmentation system 206 provides functions related to the generation andpublishing of media overlays for messages processed by the messagingsystem 100. The media overlays may be stored in the database 120 andaccessed through the database server 118.

The augmentation system 206 provides various functions that enable auser to augment (e.g., annotate or otherwise modify or edit) mediacontent associated with a message. For example, the augmentation system206 provides functions related to the generation and publishing of mediaoverlays for messages processed by the messaging system 100. Theaugmentation system 206 operatively supplies a media overlay oraugmentation (e.g., an image filter) to the messaging client 104 basedon a geolocation of the client device 102. In another example, theaugmentation system 206 operatively supplies a media overlay to themessaging client 104 based on other information, such as social networkinformation of the user of the client device 102. A media overlay mayinclude audio and visual content and visual effects. Examples of audioand visual content include pictures, texts, logos, animations, and soundeffects. An example of a visual effect includes color overlaying.

The audio and visual content or the visual effects can be applied to amedia content item (e.g., a photo) at the client device 102. In anotherexample, the media overlay includes an identification of a locationoverlay (e.g., Venice beach), a name of a live event, or a name of amerchant overlay (e.g., Beach Coffee House). In another example, theaugmentation system 206 uses the geolocation of the client device 102 toidentify a media overlay that includes the name of a merchant at thegeolocation of the client device 102. The media overlay may includeother indicia associated with the merchant. The media overlays may bestored in the database 120 and accessed through the database server 120.

In some examples, the augmentation system 206 is configured to provideaccess to AR components that can be implemented using a programminglanguage suitable for app development, such as, e.g., JavaScript or Javaand that are identified in the messaging server system by respective ARcomponent identifiers. An AR component may include or reference variousimage processing operations corresponding to an image modification,filter, media overlay, transformation, and the like. These imageprocessing operations can provide an interactive experience of areal-world environment, where objects, surfaces, backgrounds, lightingetc., captured by a digital image sensor or a camera, are enhanced bycomputer-generated perceptual information. In this context an ARcomponent comprises the collection of data, parameters, and other assetsneeded to apply a selected augmented reality experience to an image or avideo feed.

In some embodiments, an AR component includes modules configured tomodify or transform image data presented within a graphical userinterface (GUI) of a client device in some way. For example, complexadditions or transformations to the content images may be performedusing AR component data, such as adding rabbit ears to the head of aperson in a video clip, adding floating hearts with background coloringto a video clip, altering the proportions of a person's features withina video clip, or many numerous other such transformations. This includesboth real-time modifications that modify an image as it is capturedusing a camera associated with a client device and then displayed on ascreen of the client device with the AR component modifications, as wellas modifications to stored content, such as video clips in a gallerythat may be modified using AR components.

Various augmented reality functionality that may be provided by an ARcomponent include detection of objects (e.g. faces, hands, bodies, cats,dogs, surfaces, objects, etc.), tracking of such objects as they leave,enter, and move around the field of view in video frames, and themodification or transformation of such objects as they are tracked. Invarious embodiments, different methods for achieving suchtransformations may be used. For example, some embodiments may involvegenerating a 3D mesh model of the object or objects, and usingtransformations and animated textures of the model within the video toachieve the transformation. In other embodiments, tracking of points onan object may be used to place an image or texture, which may be twodimensional or three dimensional, at the tracked position. In stillfurther embodiments, neural network analysis of video frames may be usedto place images, models, or textures in content (e.g. images or framesof video). AR component data thus refers to both to the images, models,and textures used to create transformations in content, as well as toadditional modeling and analysis information needed to achieve suchtransformations with object detection, tracking, and placement.

Data Architecture

FIG. 3 is a schematic diagram illustrating data structures 300, whichmay be stored in the database 120 of the messaging server system 108,according to certain examples. While the content of the database 120 isshown to comprise a number of tables, it will be appreciated that thedata could be stored in other types of data structures (e.g., as anobject-oriented database).

The database 120 includes message data stored within a message table302. This message data includes, for any particular one message, atleast message sender data, message recipient (or receiver) data, and apayload. The payload of a message may include content generated using aviewfinder ring flash. Further details regarding information that may beincluded in a message, and included within the message data stored inthe message table 302 is described below with reference to FIG. 4 .

An entity table 304 stores entity data, and is linked (e.g.,referentially) to an entity graph 306 and profile data 308. Entities forwhich records are maintained within the entity table 304 may includeindividuals, corporate entities, organizations, objects, places, events,and so forth. Regardless of entity type, any entity regarding which themessaging server system 108 stores data may be a recognized entity. Eachentity is provided with a unique identifier, as well as an entity typeidentifier (not shown).

The entity graph 306 stores information regarding relationships andassociations between entities. Such relationships may be social,professional (e.g., work at a common corporation or organization)interested-based or activity-based, merely for example. With referenceto the functionality provided by the AR component, the entity graph 306stores information that can be used, in cases where the AR component isconfigured to permit using a portrait image of a user other than that ofthe user controlling the associated client device for modifying thetarget media content object, to determine a further profile that isconnected to the profile representing the user controlling theassociated client device. As mentioned above, the portrait image of auser may be stored in a user profile representing the user in themessaging system.

The profile data 308 stores multiple types of profile data about aparticular entity. The profile data 308 may be selectively used andpresented to other users of the messaging system 100, based on privacysettings specified by a particular entity. Where the entity is anindividual, the profile data 308 includes, for example, a user name,telephone number, address, settings (e.g., notification and privacysettings), as well as a user-selected avatar representation (orcollection of such avatar representations). A particular user may thenselectively include one or more of these avatar representations withinthe content of messages communicated via the messaging system 100, andon map interfaces displayed by messaging clients 104 to other users. Thecollection of avatar representations may include “status avatars,” whichpresent a graphical representation of a status or activity that the usermay select to communicate at a particular time.

The database 120 also stores augmentation data in an augmentation table310. The augmentation data is associated with and applied to videos (forwhich data is stored in a video table 314) and images (for which data isstored in an image table 316). In some examples, the augmentation datais used by various AR components, including the AR component. An exampleof augmentation data is augmented reality (AR) tools that can be used inAR components to effectuate image transformations. Image transformationsinclude real-time modifications, which modify an image (e.g., a videoframe) as it is captured using a digital image sensor of a client device102. The modified image is displayed on a screen of the client device102 with the modifications.

A story table 312 stores data regarding collections of messages andassociated image, video, or audio data, which are compiled into acollection (e.g., a story or a gallery). The creation of a particularcollection may be initiated by a particular user (e.g., each user forwhich a record is maintained in the entity table 304). A user may createa “personal story” in the form of a collection of content that has beencreated and sent/broadcast by that user. To this end, the user interfaceof the messaging client 104 may include an icon that is user-selectableto enable a sending user to add specific content to his or her personalstory. In some examples, the story table 312 stores one or more imagesor videos that were created using a viewfinder ring flash.

As mentioned above, the video table 314 stores video data that, in oneexample, is associated with messages for which records are maintainedwithin the message table 302. In some examples, the video table 314stores one or more videos created using a real time video editor.Similarly, the image table 316 stores image data, which may beassociated with messages for which message data is stored in the entitytable 304. The entity table 304 may associate various augmentations fromthe augmentation table 310 with various images and videos stored in theimage table 316 and the video table 314.

Data Communications Architecture

FIG. 4 is a schematic diagram illustrating a structure of a message 400,according to some examples, generated by a messaging client 104 forcommunication to a further messaging client 104 or the messaging server114. The content of a particular message 400 is used to populate themessage table 302 stored within the database 120, accessible by themessaging server 114. Similarly, the content of a message 400 is storedin memory as “in-transit” or “in-flight” data of the client device 102or the application servers 112. The content of a message 400, in someexamples, includes an image or a video that was created using the ARcomponent. A message 400 is shown to include the following examplecomponents:

-   -   message identifier 402: a unique identifier that identifies the        message 400.    -   message text payload 404: text, to be generated by a user via a        user interface of the client device 102, and that is included in        the message 400.    -   message image payload 406: image data, captured by a camera        component of a client device 102 or retrieved from a memory        component of a client device 102, and that is included in the        message 400. Image data for a sent or received message 400 may        be stored in the image table 316.    -   message video payload 408: video data, captured by a camera        component or retrieved from a memory component of the client        device 102, and that is included in the message 400. Video data        for a sent or received message 400 may be stored in the video        table 314. The video data may include content generated using a        real time video editor.    -   message audio payload 410: audio data, captured by a microphone        or retrieved from a memory component of the client device 102,        and that is included in the message 400.    -   message augmentation data 412: augmentation data (e.g., filters,        stickers, or other annotations or enhancements) that represents        augmentations to be applied to message image payload 406,        message video payload 408, message audio payload 410 of the        message 400. Augmentation data for a sent or received message        400 may be stored in the augmentation table 310.    -   message duration parameter 414: parameter value indicating, in        seconds, the amount of time for which content of the message        (e.g., the message image payload 406, message video payload 408,        message audio payload 410) is to be presented or made accessible        to a user via the messaging client 104.    -   message geolocation parameter 416: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message. Multiple message geolocation        parameter 416 values may be included in the payload, each of        these parameter values being associated with respect to content        items included in the content (e.g., a specific image into        within the message image payload 406, or a specific video in the        message video payload 408).    -   message story identifier 418: identifier values identifying one        or more content collections (e.g., “stories” identified in the        story table 312) with which a particular content item in the        message image payload 406 of the message 400 is associated. For        example, multiple images within the message image payload 406        may each be associated with multiple content collections using        identifier values.    -   message tag 420: each message 400 may be tagged with multiple        tags, each of which is indicative of the subject matter of        content included in the message payload. For example, where a        particular image included in the message image payload 406        depicts an animal (e.g., a lion), a tag value may be included        within the message tag 420 that is indicative of the relevant        animal. Tag values may be generated manually, based on user        input, or may be automatically generated using, for example,        image recognition.    -   message sender identifier 422: an identifier (e.g., a messaging        system identifier, email address, or device identifier)        indicative of a user of the Client device 102 on which the        message 400 was generated and from which the message 400 was        sent.    -   message receiver identifier 424: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 to        which the message 400 is addressed.

The contents (e.g., values) of the various components of message 400 maybe pointers to locations in tables within which content data values arestored. For example, an image value in the message image payload 406 maybe a pointer to (or address of) a location within an image table 316.Similarly, values within the message video payload 408 may point to datastored within a video table 314, values stored within the messageaugmentations 412 may point to data stored in an augmentation table 310,values stored within the message story identifier 418 may point to datastored in a story table 312, and values stored within the message senderidentifier 422 and the message receiver identifier 424 may point to userrecords stored within an entity table 304.

Time-Based Access Limitation Architecture

FIG. 5 is a schematic diagram illustrating an access-limiting process500, in terms of which access to content (e.g., an ephemeral message502, and associated multimedia payload of data) or a content collection(e.g., an ephemeral message group 504) may be time-limited (e.g., madeephemeral). The content of an ephemeral message 502, in some examples,includes an image or a video that was created using a viewfinder ringflash.

An ephemeral message 502 is shown to be associated with a messageduration parameter 506, the value of which determines an amount of timethat the ephemeral message 502 will be displayed to a receiving user ofthe ephemeral message 502 by the messaging client 104. In one example,an ephemeral message 502 is viewable by a receiving user for up to amaximum of 10 seconds, depending on the amount of time that the sendinguser specifies using the message duration parameter 506. In someexamples, the ephemeral message 502 may include a video created using areal time video editor.

The message duration parameter 506 and the message receiver identifier424 are shown to be inputs to a message timer 512, which is responsiblefor determining the amount of time that the ephemeral message 502 isshown to a particular receiving user identified by the message receiveridentifier 424. In particular, the ephemeral message 502 will only beshown to the relevant receiving user for a time period determined by thevalue of the message duration parameter 506. The message timer 512 isshown to provide output to a more generalized ephemeral timer system202, which is responsible for the overall timing of display of content(e.g., an ephemeral message 502) to a receiving user.

The ephemeral message 502 is shown in FIG. 5 to be included within anephemeral message group 504 (e.g., a collection of messages in apersonal story, or an event story). The ephemeral message group 504 hasan associated group duration parameter 508, a value of which determinesa time duration for which the ephemeral message group 504 is presentedand accessible to users of the messaging system 100. The group durationparameter 508, for example, may be the duration of a music concert,where the ephemeral message group 504 is a collection of contentpertaining to that concert. Alternatively, a user (either the owninguser or a curator user) may specify the value for the group durationparameter 508 when performing the setup and creation of the ephemeralmessage group 504.

Additionally, each ephemeral message 502 within the ephemeral messagegroup 504 has an associated group participation parameter 510, a valueof which determines the duration of time for which the ephemeral message502 will be accessible within the context of the ephemeral message group504. Accordingly, a particular ephemeral message group 504 may “expire”and become inaccessible within the context of the ephemeral messagegroup 504, prior to the ephemeral message group 504 itself expiring interms of the group duration parameter 508. The group duration parameter508, group participation parameter 510, and message receiver identifier424 each provide input to a group timer 514, which operationallydetermines, firstly, whether a particular ephemeral message 502 of theephemeral message group 504 will be displayed to a particular receivinguser and, if so, for how long. Note that the ephemeral message group 504is also aware of the identity of the particular receiving user as aresult of the message receiver identifier 424.

Accordingly, the group timer 514 operationally controls the overalllifespan of an associated ephemeral message group 504, as well as anindividual ephemeral message 502 included in the ephemeral message group504. In one example, each and every ephemeral message 502 within theephemeral message group 504 remains viewable and accessible for a timeperiod specified by the group duration parameter 508. In a furtherexample, a certain ephemeral message 502 may expire, within the contextof ephemeral message group 504, based on a group participation parameter510. Note that a message duration parameter 506 may still determine theduration of time for which a particular ephemeral message 502 isdisplayed to a receiving user, even within the context of the ephemeralmessage group 504. Accordingly, the message duration parameter 506determines the duration of time that a particular ephemeral message 502is displayed to a receiving user, regardless of whether the receivinguser is viewing that ephemeral message 502 inside or outside the contextof an ephemeral message group 504.

The ephemeral timer system 202 may furthermore operationally remove aparticular ephemeral message 502 from the ephemeral message group 504based on a determination that it has exceeded an associated groupparticipation parameter 510. For example, when a sending user hasestablished a group participation parameter 510 of 24 hours fromposting, the ephemeral timer system 202 will remove the relevantephemeral message 502 from the ephemeral message group 504 after thespecified 24 hours. The ephemeral timer system 202 also operates toremove an ephemeral message group 504 when either the groupparticipation parameter 510 for each and every ephemeral message 502within the ephemeral message group 504 has expired, or when theephemeral message group 504 itself has expired in terms of the groupduration parameter 508.

In certain use cases, a creator of a particular ephemeral message group504 may specify an indefinite group duration parameter 508. In thiscase, the expiration of the group participation parameter 510 for thelast remaining ephemeral message 502 within the ephemeral message group504 will determine when the ephemeral message group 504 itself expires.In this case, a new ephemeral message 502, added to the ephemeralmessage group 504, with a new group participation parameter 510,effectively extends the life of an ephemeral message group 504 to equalthe value of the group participation parameter 510.

Responsive to the ephemeral timer system 202 determining that anephemeral message group 504 has expired (e.g., is no longer accessible),the ephemeral timer system 202 communicates with the messaging system100 (and, for example, specifically the messaging client 104) to causean indicium (e.g., an icon) associated with the relevant ephemeralmessage group 504 to no longer be displayed within a user interface ofthe messaging client 104. Similarly, when the ephemeral timer system 202determines that the message duration parameter 506 for a particularephemeral message 502 has expired, the ephemeral timer system 202 causesthe messaging client 104 to no longer display an indicium (e.g., an iconor textual identification) associated with the ephemeral message 502.

Process Flow and User Interfaces

FIG. 6 is a flowchart illustrating a method 600 for real time videoediting in accordance with some examples. While certain operations ofthe process 600 may be described as being performed by certain devices,in different examples, different devices or a combination of devices mayperform these operations. For example, operations described below may beperformed by the client device 102 or in combination with a server-sidecomputing device (e.g., the message messaging server system 108).

The method 600 starts at operation 610, with commencing a videorecording process by a camera of a client device. The video recordingprocess, while in progress, produces a sequence of frames, each framefrom the sequence of frames associated with a time stamp. The resultingvideo is not finalized until the video recording process is ended, atwhich time the resulting video is finalized (encoded into a desiredformat, for example, and saved for future access). The commencing of thevideo recording process occurs, in some examples, in response toactivation of a shutter user selectable element in a camera view userinterface (UI) displayed at a client device. An example of a camera viewUI is shown in FIG. 7 . FIG. 7 is a diagrammatic representation 700 of acamera view UI displaying the output of the digital image sensor of acamera. The output of the digital sensor of a camera is represented inarea 710, showing the sky with clouds in this example. The camera viewUI shown in FIG. 7 also includes a shutter user selectable element 720.In some examples, the camera view UI is provided by the messaging systemfor exchanging data over a network described above, with reference toFIG. 1-5 .

At operation 620, while the video recording process is in progress, thereal time video editor detects a gesture directed at the camera view UI.The gesture can be, for example, a left to right swiping gesture, asillustrated in FIG. 8 . FIG. 8 is a diagrammatic representation 800 of aleft to right swiping gesture directed at the camera view UI displayingthe output of the digital image sensor of the camera in area 820. InFIG. 8 , the curved arrow pointing right and the stylized picture of ahand with a pointing finger, identified by reference numeral 810, arenot part of the camera view UI, but rather a visualization of a swipingleft to right gesture.

In response to the detecting of the gesture, the real time video editorcauses displaying the captured frames in a reverse order (in adescending order based on respective time stamps of the frames), in amanner imitating rewinding of the video. The displaying of the capturedframes in a sequential reverse order continues until the gesture stops,at which point the currently displayed frame is considered to bepotentially a new starting point of a video that would result from thevideo recording process. The frame displayed in the camera view UI atthe time the swiping gesture stops is referred to as a new first frame,for the purposes of this description.

At operation 630, in response to the detecting of the gesture, the realtime video editor causes displaying of the new first frame, where thenew first frame is selected based on the duration of the gesture. Forexample, if the gesture is brief, the sequence of frames being capturedis rewound just a few frames back. If the gesture is longer, thesequence of frames is rewound further back. In some examples, the realtime video editor may use, in addition to or instead of the duration,other characteristics of the gesture, such as speed, acceleration, andso on. The time stamp of the new first frame indicates a point in timeprior to a time when the gesture was detected.

FIG. 9 is a diagrammatic representation 900 of a of a rewind actionimitation in a camera view user interface, in accordance with someexamples. In FIG. 9 , the curved arrow pointing right and the stylizedpicture of a hand with a pointing finger, identified by referencenumeral 910, are not part of the camera view UI, but rather avisualization of a swiping left to right swiping gesture. Compared toFIG. 8 , the stylized picture of a hand in FIG. 9 has a finger pointingto the right, which is a visualization of the ending of the gestureduration. Furthermore, while in FIG. 7 , which is a visualization of oneof the earlier frames with respect to commencement of the videorecording, the output of a digital sensor of the camera in area 710shows an empty sky with clouds, while in FIG. 8 the corresponding area820 shows two planes, which is a visualization of an event that a usermay have been expecting and wishing to capture in a video. In FIG. 9 ,frame 920 shows one plane, while frames 930 and 940 show just clouds,which is a visualization of the event of interest—arrival of the firstplane in the sky—that occurred contemporaneously with capturing of frame940. The real time video editing methodology described herein permits auser to “rewind” the video in real time, while the recording session isstill in progress, and set the new starting point for the video, e.g.,starting with the frame 940.

In some examples, subsequent to the displaying a new first frame fromthe sequence of frames in the camera view UI, and while the videorecording process is still in progress, the real time video editorobtains from a user a selection or confirmation to identify the newfirst frame as a new starting point of the video recording process. Theobtaining of the selection may be in the form of a presentation of auser selectable element overlaid over the new first frame presented inthe camera view UI. In order to make the new first frame a new startingpoint of the video that would result from the video recording process,the real time video editor may be configured to discard frames with timestamps indicating time prior to the time stamp of the new first frame(in other words, starting with the new first frame).

At operation 640, in response to ending or stopping of the videorecording process, the real time vide editor generates a video fileusing frames captured during the video recording process, starting withthe new first frame except for frames with time stamps indicatingearlier time than the time stamp of the new first frame. The ending ofthe video recording process may be in response to a further activationof a shutter user selectable element in a camera view UI.

Machine Architecture

FIG. 10 is a diagrammatic representation of the machine 1000 withinwhich instructions 1008 (e.g., software, a program, an application, anapplet, an app, or other executable code) for causing the machine 1000to perform any one or more of the methodologies discussed herein may beexecuted. For example, the instructions 1008 may cause the machine 1000to execute any one or more of the methods described herein. Theinstructions 1008 transform the general, non-programmed machine 1000into a particular machine 1000 programmed to carry out the described andillustrated functions in the manner described. The machine 1000 mayoperate as a standalone device or may be coupled (e.g., networked) toother machines. In a networked deployment, the machine 1000 may operatein the capacity of a server machine or a client machine in aserver-client network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. The machine 1000 maycomprise, but not be limited to, a server computer, a client computer, apersonal computer (PC), a tablet computer, a laptop computer, a netbook,a set-top box (STB), a personal digital assistant (PDA), anentertainment media system, a cellular telephone, a smartphone, a mobiledevice, a wearable device (e.g., a smartwatch), a smart home device(e.g., a smart appliance), other smart devices, a web appliance, anetwork router, a network switch, a network bridge, or any machinecapable of executing the instructions 1008, sequentially or otherwise,that specify actions to be taken by the machine 1000. Further, whileonly a single machine 1000 is illustrated, the term “machine” shall alsobe taken to include a collection of machines that individually orjointly execute the instructions 1008 to perform any one or more of themethodologies discussed herein. The machine 1000, for example, maycomprise the client device 102 or any one of a number of server devicesforming part of the messaging server system 108. In some examples, themachine 1000 may also comprise both client and server systems, withcertain operations of a particular method or algorithm being performedon the server-side and with certain operations of the particular methodor algorithm being performed on the client-side.

The machine 1000 may include processors 1002, memory 1004, andinput/output I/O components 1038, which may be configured to communicatewith each other via a bus 1040. In an example, the processors 1002(e.g., a Central Processing Unit (CPU), a Reduced Instruction SetComputing (RISC) Processor, a Complex Instruction Set Computing (CISC)Processor, a Graphics Processing Unit (GPU), a Digital Signal Processor(DSP), an Application Specific Integrated Circuit (ASIC), aRadio-Frequency Integrated Circuit (RFIC), another processor, or anysuitable combination thereof) may include, for example, a processor 1006and a processor 1010 that execute the instructions 1008. The term“processor” is intended to include multi-core processors that maycomprise two or more independent processors (sometimes referred to as“cores”) that may execute instructions contemporaneously. Although FIG.10 shows multiple processors 1002, the machine 1000 may include a singleprocessor with a single-core, a single processor with multiple cores(e.g., a multi-core processor), multiple processors with a single core,multiple processors with multiples cores, or any combination thereof.

The memory 1004 includes a main memory 1012, a static memory 1014, and astorage unit 1016, both accessible to the processors 1002 via the bus1040. The main memory 1004, the static memory 1014, and storage unit1016 store the instructions 1008 embodying any one or more of themethodologies or functions described herein. The instructions 1008 mayalso reside, completely or partially, within the main memory 1012,within the static memory 1014, within machine-readable medium 1018within the storage unit 1016, within at least one of the processors 1002(e.g., within the Processor's cache memory), or any suitable combinationthereof, during execution thereof by the machine 1000.

The I/O components 1038 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1038 that are included in a particular machine will depend onthe type of machine. For example, portable machines such as mobilephones may include a touch input device or other such input mechanisms,while a headless server machine will likely not include such a touchinput device. It will be appreciated that the I/O components 1038 mayinclude many other components that are not shown in FIG. 10 . In variousexamples, the I/O components 1038 may include user output components1024 and user input components 1026. The user output components 1024 mayinclude visual components (e.g., a display such as a plasma displaypanel (PDP), a light-emitting diode (LED) display, a liquid crystaldisplay (LCD), a projector, or a cathode ray tube (CRT)), acousticcomponents (e.g., speakers), haptic components (e.g., a vibratory motor,resistance mechanisms), other signal generators, and so forth. The userinput components 1026 may include alphanumeric input components (e.g., akeyboard, a touch screen configured to receive alphanumeric input, aphoto-optical keyboard, or other alphanumeric input components),point-based input components (e.g., a mouse, a touchpad, a trackball, ajoystick, a motion sensor, or another pointing instrument), tactileinput components (e.g., a physical button, a touch screen that provideslocation and force of touches or touch gestures, or other tactile inputcomponents), audio input components (e.g., a microphone), and the like.

In further examples, the I/O components 1038 may include biometriccomponents 1028, motion components 1030, environmental components 1032,or position components 1034, among a wide array of other components. Forexample, the biometric components 1028 include components to detectexpressions (e.g., hand expressions, facial expressions, vocalexpressions, body gestures, or eye-tracking), measure biosignals (e.g.,blood pressure, heart rate, body temperature, perspiration, or brainwaves), identify a person (e.g., voice identification, retinalidentification, facial identification, fingerprint identification, orelectroencephalogram-based identification), and the like. The motioncomponents 1030 include acceleration sensor components (e.g.,accelerometer), gravitation sensor components, rotation sensorcomponents (e.g., gyroscope).

The environmental components 1032 include, for example, one or morecameras (with still image/photograph and video capabilities),illumination sensor components (e.g., photometer), temperature sensorcomponents (e.g., one or more thermometers that detect ambienttemperature), humidity sensor components, pressure sensor components(e.g., barometer), acoustic sensor components (e.g., one or moremicrophones that detect background noise), proximity sensor components(e.g., infrared sensors that detect nearby objects), gas sensors (e.g.,gas detection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment.

With respect to cameras, the client device 102 may have a camera systemcomprising, for example, front facing cameras on a front surface of theclient device 102 and rear cameras on a rear surface of the clientdevice 102. The front facing cameras may, for example, be used tocapture still images and video of a user of the client device 102 (e.g.,“selfies”), which may then be augmented with augmentation data (e.g.,filters) described above. In the examples where the front facing camerais used with a viewfinder ring flash described herein, the user has theability to use augmented reality face filters in low light conditions,even in complete darkness, as the viewfinder ring flash illuminates theuser's face without obscuring the output of the digital image sensor.The rear cameras may, for example, be used to capture still images andvideos in a more traditional camera mode, with these images similarlybeing augmented with augmentation data. In addition to front and rearcameras, the client device 102 may also include a 360° camera forcapturing 360° photographs and videos.

Further, the camera system of a client device 102 may include dual rearcameras (e.g., a primary camera as well as a depth-sensing camera), oreven triple, quad or penta rear camera configurations on the front andrear sides of the client device 102. These multiple cameras systems mayinclude a wide camera, an ultra-wide camera, a telephoto camera, a macrocamera and a depth sensor, for example.

The position components 1034 include location sensor components (e.g., aGPS receiver component), altitude sensor components (e.g., altimeters orbarometers that detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1038 further include communication components 1036operable to couple the machine 1000 to a network 1020 or devices 1022via respective coupling or connections. For example, the communicationcomponents 1036 may include a network interface Component or anothersuitable device to interface with the network 1020. In further examples,the communication components 1036 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 1022 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a USB).

Moreover, the communication components 636 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 636 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF410, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components1036, such as location via Internet Protocol (IP) geolocation, locationvia Wi-Fi® signal triangulation, location via detecting an NFC beaconsignal that may indicate a particular location, and so forth.

The various memories (e.g., main memory 1012, static memory 1014, andmemory of the processors 1002) and storage unit 1016 may store one ormore sets of instructions and data structures (e.g., software) embodyingor used by any one or more of the methodologies or functions describedherein. These instructions (e.g., the instructions 1008), when executedby processors 1002, cause various operations to implement the disclosedexamples.

The instructions 1008 may be transmitted or received over the network1020, using a transmission medium, via a network interface device (e.g.,a network interface component included in the communication components1036) and using any one of several well-known transfer protocols (e.g.,hypertext transfer protocol (HTTP)). Similarly, the instructions 1008may be transmitted or received using a transmission medium via acoupling (e.g., a peer-to-peer coupling) to the devices 1022.

Glossary

“Carrier signal” refers to any intangible medium that is capable ofstoring, encoding, or carrying instructions for execution by themachine, and includes digital or analog communications signals or otherintangible media to facilitate communication of such instructions.Instructions may be transmitted or received over a network using atransmission medium via a network interface device.

“Client device” refers to any machine that interfaces to acommunications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, portable digitalassistants (PDAs), smartphones, tablets, ultrabooks, netbooks, laptops,multi-processor systems, microprocessor-based or programmable consumerelectronics, game consoles, set-top boxes, or any other communicationdevice that a user may use to access a network.

“Communication network” refers to one or more portions of a network thatmay be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the PublicSwitched Telephone Network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a Wi-Fi®&network, another type of network, or a combination of two or more suchnetworks. For example, a network or a portion of a network may include awireless or cellular network and the coupling may be a Code DivisionMultiple Access (CDMA) connection, a Global System for Mobilecommunications (GSM) connection, or other types of cellular or wirelesscoupling. In this example, the coupling may implement any of a varietyof types of data transfer technology, such as Single Carrier RadioTransmission Technology (1×RTT), Evolution-Data Optimized (EVDO)technology, General Packet Radio Service (GPRS) technology, EnhancedData rates for GSM Evolution (EDGE) technology, third GenerationPartnership Project (3GPP) including 3G, fourth generation wireless (4G)networks, Universal Mobile Telecommunications System (UMTS), High SpeedPacket Access (HSPA), Worldwide Interoperability for Microwave Access(WiMAX), Long Term Evolution (LTE) standard, others defined by variousstandard-setting organizations, other long-range protocols, or otherdata transfer technology.

“Component” refers to a device, physical entity, or logic havingboundaries defined by function or subroutine calls, branch points, APIs,or other technologies that provide for the partitioning ormodularization of particular processing or control functions. Componentsmay be combined via their interfaces with other components to carry outa machine process. A component may be a packaged functional hardwareunit designed for use with other components and a part of a program thatusually performs a particular function of related functions. Componentsmay constitute either software components (e.g., code embodied on amachine-readable medium) or hardware components. A “hardware component”is a tangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleexamples, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware components of a computer system (e.g., a processor or agroup of processors) may be configured by software (e.g., an applicationor application portion) as a hardware component that operates to performcertain operations as described herein. A hardware component may also beimplemented mechanically, electronically, or any suitable combinationthereof. For example, a hardware component may include dedicatedcircuitry or logic that is permanently configured to perform certainoperations. A hardware component may be a special-purpose processor,such as a field-programmable gate array (FPGA) or an applicationspecific integrated circuit (ASIC). A hardware component may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwarecomponent may include software executed by a general-purpose processoror other programmable processor. Once configured by such software,hardware components become specific machines (or specific components ofa machine) uniquely tailored to perform the configured functions and areno longer general-purpose processors. It will be appreciated that thedecision to implement a hardware component mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software), may be driven by cost and timeconsiderations. Accordingly, the phrase “hardware component” (or“hardware-implemented component”) should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering examples in which hardwarecomponents are temporarily configured (e.g., programmed), each of thehardware components need not be configured or instantiated at any oneinstance in time. For example, where a hardware component comprises ageneral-purpose processor configured by software to become aspecial-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware components) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware component at one instanceof time and to constitute a different hardware component at a differentinstance of time. Hardware components can provide information to, andreceive information from, other hardware components. Accordingly, thedescribed hardware components may be regarded as being communicativelycoupled. Where multiple hardware components exist contemporaneously,communications may be achieved through signal transmission (e.g., overappropriate circuits and buses) between or among two or more of thehardware components. In examples in which multiple hardware componentsare configured or instantiated at different times, communicationsbetween such hardware components may be achieved, for example, throughthe storage and retrieval of information in memory structures to whichthe multiple hardware components have access. For example, one hardwarecomponent may perform an operation and store the output of thatoperation in a memory device to which it is communicatively coupled. Afurther hardware component may then, at a later time, access the memorydevice to retrieve and process the stored output. Hardware componentsmay also initiate communications with input or output devices, and canoperate on a resource (e.g., a collection of information). The variousoperations of example methods described herein may be performed, atleast partially, by one or more processors that are temporarilyconfigured (e.g., by software) or permanently configured to perform therelevant operations. Whether temporarily or permanently configured, suchprocessors may constitute processor-implemented components that operateto perform one or more operations or functions described herein. As usedherein, “processor-implemented component” refers to a hardware componentimplemented using one or more processors. Similarly, the methodsdescribed herein may be at least partially processor-implemented, with aparticular processor or processors being an example of hardware. Forexample, at least some of the operations of a method may be performed byone or more processors or processor-implemented components. Moreover,the one or more processors may also operate to support performance ofthe relevant operations in a “cloud computing” environment or as a“software as a service” (SaaS). For example, at least some of theoperations may be performed by a group of computers (as examples ofmachines including processors), with these operations being accessiblevia a network (e.g., the Internet) and via one or more appropriateinterfaces (e.g., an API). The performance of certain of the operationsmay be distributed among the processors, not only residing within asingle machine, but deployed across a number of machines. In someexample examples, the processors or processor-implemented components maybe located in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleexamples, the processors or processor-implemented components may bedistributed across a number of geographic locations.

“Computer-readable storage medium” refers to both machine-storage mediaand transmission media. Thus, the terms include both storagedevices/media and carrier waves/modulated data signals. The terms“machine-readable medium,” “computer-readable medium” and“device-readable medium” mean the same thing and may be usedinterchangeably in this disclosure.

“Machine storage medium” refers to a single or multiple storage devicesand media (e.g., a centralized or distributed database, and associatedcaches and servers) that store executable instructions, routines anddata. The term shall accordingly be taken to include, but not be limitedto, solid-state memories, and optical and magnetic media, includingmemory internal or external to processors. Specific examples ofmachine-storage media, computer-storage media and device-storage mediainclude non-volatile memory, including by way of example semiconductormemory devices, e.g., erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), FPGA, andflash memory devices; magnetic disks such as internal hard disks andremovable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks Theterms “machine-storage medium,” “device-storage medium,”“computer-storage medium” mean the same thing and may be usedinterchangeably in this disclosure. The terms “machine-storage media,”“computer-storage media,” and “device-storage media” specificallyexclude carrier waves, modulated data signals, and other such media, atleast some of which are covered under the term “signal medium.”

“Non-transitory computer-readable storage medium” refers to a tangiblemedium that is capable of storing, encoding, or carrying theinstructions for execution by a machine.

“Signal medium” refers to any intangible medium that is capable ofstoring, encoding, or carrying the instructions for execution by amachine and includes digital or analog communications signals or otherintangible media to facilitate communication of software or data. Theterm “signal medium” shall be taken to include any form of a modulateddata signal, carrier wave, and so forth. The term “modulated datasignal” means a signal that has one or more of its characteristics setor changed in such a matter as to encode information in the signal. Theterms “transmission medium” and “signal medium” mean the same thing andmay be used interchangeably in this disclosure.

What is claimed is:
 1. A method comprising: commencing a video recordingprocess by a camera of a client device, the video recording processproducing a sequence of frames, each frame from the sequence of framesassociated with a time stamp; while the video recording process is inprogress, detecting a gesture directed at a camera view user interface(UI) displayed at the client device; in response to the detecting of thegesture, causing displaying a new first frame from the sequence offrames in the camera view UI, based on duration of the gesture, a timestamp of the new first frame indicating time prior to a time when thegesture was detected; in response to ending of the video recordingprocess, generating a video file using frames captured during the videorecording process, except for frames with time stamps indicating earliertime than the time stamp of the new first frame.
 2. The method of claim1, comprising: in response to the detecting of the gesture, commencingdisplaying, sequentially, in the camera view UI, frames from thesequence of frames in a descending order based on respective time stampsof frames from the sequence of frames.
 3. The method of claim 1,comprising: subsequent to the displaying the new first frame from thesequence of frames in the camera view UI, and while the video recordingprocess is in progress, obtaining a selection from a user to identifythe new first frame as a new starting point of the video recordingprocess.
 4. The method of claim 3, wherein the obtaining of theselection comprises presentation of a user selectable element overlaidover the new first frame presented in the camera view UI.
 5. The methodof claim 1, comprising: from the sequence of video frames, discardingframes with respective time stamps indicating time prior to the timestamp of the new first frame.
 6. The method of claim 1, wherein thegesture is a left to right swiping gesture.
 7. The method of claim 1,wherein the determining of the new first frame from the sequence offrames is based on duration of the gesture.
 8. The method of claim 1,wherein the commencing of the video recording process is in response toactivation of a shutter user selectable element in the camera view UI,the camera view UI comprising output of a digital sensor of the camera.9. The method of claim 8, wherein the ending of the video recordingprocess is in response to a further activation of the shutter userselectable element in the camera view UI.
 10. The method of claim 1,wherein the camera view UI is provided by a messaging system forexchanging data over a network.
 11. A system comprising: one or moreprocessors; and a non-transitory computer readable storage mediumcomprising instructions that when executed by the one or processorscause the one or more processors to perform operations comprising:commencing a video recording process by a camera of a client device, thevideo recording process producing a sequence of frames, each frame fromthe sequence of frames associated with a time stamp; while the videorecording process is in progress, detecting a gesture directed at acamera view user interface (UI) displayed at the client device; inresponse to the detecting of the gesture, causing displaying a new firstframe from the sequence of frames in the camera view UI, based onduration of the gesture, a time stamp of the new first frame indicatingtime prior to a time when the gesture was detected; in response toending of the video recording process, generating a video file usingframes captured during the video recording process, except for frameswith time stamps indicating earlier time than the time stamp of the newfirst frame.
 12. The system of claim 11, wherein the operations causedby instructions executed by the one or processors further include: inresponse to the detecting of the gesture, commencing displaying,sequentially, in the camera view UI, frames from the sequence of framesin a descending order based on respective time stamps of frames from thesequence of frames.
 13. The system of claim 11, wherein the operationscaused by instructions executed by the one or processors furtherinclude: subsequent to the displaying the new first frame from thesequence of frames in the camera view UI, and while the video recordingprocess is in progress, obtaining a selection from a user to identifythe new first frame as a new starting point of the video recordingprocess.
 14. The system of claim 13, wherein the obtaining of theselection comprises presentation of a user selectable element overlaidover the new first frame presented in the camera view UI.
 15. The systemof claim 11, wherein the operations caused by instructions executed bythe one or processors further include: from the sequence of videoframes, discarding frames with respective time stamps indicating timeprior to the time stamp of the new first frame.
 16. The system of claim11, wherein the gesture is a left to right swiping gesture.
 17. Thesystem of claim 11, wherein the determining of the new first frame fromthe sequence of frames is based on duration of the gesture.
 18. Thesystem of claim 11, wherein the commencing of the video recordingprocess is in response to activation of a shutter user selectableelement in the camera view UI, the camera view UI comprising output of adigital sensor of the camera.
 19. The system of claim 18, wherein theending of the video recording process is in response to a furtheractivation of the shutter user selectable element in the camera view UI.20. A machine-readable non-transitory storage medium having instructiondata executable by a machine to cause the machine to perform operationscomprising: commencing a video recording process by a camera of a clientdevice, the video recording process producing a sequence of frames, eachframe from the sequence of frames associated with a time stamp; whilethe video recording process is in progress, detecting a gesture directedat a camera view user interface (UI) displayed at the client device; inresponse to the detecting of the gesture, causing displaying a new firstframe from the sequence of frames in the camera view UI, based onduration of the gesture, a time stamp of the new first frame indicatingtime prior to a time when the gesture was detected; in response toending of the video recording process, generating a video file usingframes captured during the video recording process, except for frameswith time stamps indicating earlier time than the time stamp of the newfirst frame.